Automatic creation and updating of event group summaries

ABSTRACT

A disclosed computer-implemented method includes receiving and indexing the raw data. Indexing includes dividing the raw data into time stamped searchable events that include information relating to computer or network security. Store the indexed data in an indexed data store and extract values from a field in the indexed data using a schema. Search the extracted field values for the security information. Determine a group of security events using the security information. Each security event includes a field value specified by a criteria. Present a graphical interface (GI) including a summary of the group of security events, other summaries of security events, and a remove element (associated with the summary). Receive input corresponding to an interaction of the remove element. Interacting with the remove element causes the summary to be removed from the GI. Update the GI to remove the summary from the GI.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/526,354, filed on Jul. 30, 2019, which is a continuation of U.S.patent application Ser. No. 15/996,866, filed on Jun. 4, 2018, now U.S.Pat. No. 10,382,472, which is a continuation of U.S. patent applicationSer. No. 15/421,420, filed on Jan. 31, 2017, now U.S. Pat. No.9,992,220, which is a continuation of U.S. patent application Ser. No.15/056,999, filed on Feb. 29, 2016, now U.S. Pat. No. 9,596,252, whichis a continuation of U.S. patent application Ser. No. 14/280,311, filedon May 16, 2014, now U.S. Pat. No. 9,276,946, which is a continuation ofU.S. patent application Ser. No. 13/956,285, filed on Jul. 31, 2013 nowU.S. Pat. No. 8,752,178, the entire contents of the foregoing are herebyincorporated by reference as if fully set forth herein. The applicanthereby rescinds any disclaimer of claim scope in the parent applicationsor the prosecution history thereof and advise the USPTO that the claimsin this application may be broader than any claim in the parentapplications.

TECHNICAL FIELD

The present disclosure relates generally to computer-implemented systemsand methods for managing data associated with events in a securityinformation and event management environment.

BACKGROUND

A security management system, such as a security information and eventmanagement (SIEM) system, provide a computing environment that enablesreal-time analysis of security-related events generated based computingactivity. A SIEM system may also provide analytical tools having a rangeof functions including trend analysis, event identification, andalerting.

Despite having an implemented SIEM system, enterprises continue tobattle a host of security vulnerabilities in their informationtechnology (IT) systems as distributed computing systems are rapidlyadopted and expanded by the enterprises. With an expansion ofdistributed computing systems comes additional security issues due tothe addition of the new components and the communications between thesecomponents. Such changes may introduce new challenges for monitoring andanalyzing security events based on activity occurring in the distributedcomputing systems.

Often, a user of a SIEM system may be presented with large amounts ofdata relating to security events occurring in the system. Left with adifficult task of sorting through the data to identify significant, ornoteworthy events, the user faces an additional challenge of indicatingor flagging events to be distinguished from each other. The user maydesire to exclude events of little relevance or alternatively may wishto flag events of importance such as those relating to potentialsecurity threats. It may be useful for an analyst to be provided with atool that, besides presenting information related to events, enables theanalyst to filter such events to efficiently identify important events,such as those related to a security threat.

SUMMARY

In accordance with the teachings provided herein, systems and methodsare disclosed for monitoring and filtering events in a security eventmanagement system or a security information and event management system(SIEM). More specifically, these systems and methods may improveefficiency for identifying and filtering events that are related to apotential security threat requiring further investigation. The eventsmay be based on computer activity including access control to a system,activity at an endpoint in a system, and/or network activity. Events maybe identified in raw data (e.g., machine data, unstructured data, and/orweblogs) based on a time stamp. Each event may be stored as a time-basedevent in a data store (e.g., a time-series data store) using anappropriate index corresponding to a time stamp of the event. The timestamped stored events may include information related to computersecurity or network security, such as network information (e.g., httpagent strings, network traffic size, a length of a uniform resourcelocator string, byte count per request, domain names, or a sourceaddress), access control information (e.g., login/logout information oraccess failures), or endpoint information (e.g., malware infections,system configurations, or system states).

To facilitate identification of security-related events (e.g., eventsthat may be relevant to computer or network security), a disclosedsystem may perform further processing on time stamped events to identifyevents having information related to computer or network security. Theinformation related to computer or network security may include anyinformation that is useful for analysis of the time stamped event toidentify a potential issue with security. For example, the securityinformation may include http user agent strings, network traffic size, alength of a uniform resource locator string, byte count per request,domain names, or source address, any of which may indicate or be used todetermine whether a time stamped event poses a security threat. Fieldvalues may be extracted from indexed data corresponding to the timestamped events, and then searched for the security information toidentify security related events.

The events identified based on the security information may be groupedtogether based on one or more fields in each of the events satisfying acriteria for a group of security-related events. The criteria may bedefined based on one or more fields that contain information usefulindicative of a potential security threat. A group of security-relatedevents that include these fields may be useful for identifying a sourceof such malicious activity. Thus, groups of security-related events mayindicate a relationship of events that are related to a type of securityissue.

Embodiments disclosed herein improve efficiency for identification ofgroups of events related to a particular type of security issue. Thesystems and methods disclosed herein provide a graphical interface thatdisplays one or more summaries, each summary corresponding to group ofevents identified based on criteria used to identify a specific type ofevents based on security information. The summary may includeinformation that summarizes the group of events associated with thesummary. The information may include details including a count of thenumber of events in the group of security events. The information mayinclude a metric representing a summary or calculation based on thecount and/or one or more fields in each event of the group of securityevents. The summary may include one or more fields determined basedfields in one or more security events of the group. In particularembodiments, the summary may be a selectable element that enablesdisplay of information of the underlying group of security events forthe summary.

Disclosed embodiments provide one or more interactive elements (e.g.,selectable controls) associated with a summary in the graphicalinterface to enable selective filtering of the summary. One suchinteractive element may be a remove element (e.g., a selectable control)for removing (“whitelisting”) a summary from the graphical interface toindicate that the summary and/or related groups of events are acceptable(e.g., do not pose a security threat). Another interactive elementassociated with the summary may include a modify element for modifying(“blacklisting”) a visual appearance of the summary (e.g., highlight orchange a position) in the graphical interface to indicate that thesummary and/or related groups of events pose a potential securitythreat.

A display may be provided to view summaries that have been whitelistedand/or blacklisted from the graphical interface. The display may includeinteractive elements to cause a whitelisted summary to be added back tothe graphical interface. The display may include interactive elements tocauses modification to a blacklisted summary to be undone. Thus,embodiments disclosed herein reduce effort involved to selectivelyfilter events related to computing or network security. The graphicalinterface further enables events based on new received raw data toprocessed and the graphical interface to be updated for events thatbelong to a group of events in one or more summaries in the graphicalinterface.

In a particular embodiment, a computer-implemented method is provided.The computer-implemented method includes receiving, on a computingdevice, raw data and indexing the raw data. Indexing includes dividingthe raw data into time stamped searchable events that includeinformation relating to computer or network security. Thecomputer-implemented method includes storing the indexed data in anindexed data store. The computer-implemented method includes extractingone or more values from a field in the indexed data using a schema. Thecomputer-implemented method includes searching the one or more extractedfield values for the security information. The computer-implementedmethod includes determining a group of security events. The group ofsecurity events is determined using the security information. Eachsecurity event of the group of security events includes a field valuespecified by a criteria. The computer-implemented method includespresenting a graphical interface including a summary of the group ofsecurity events, other summaries of security events, and a removeelement. The remove element is associated with the summary. Thecomputer-implemented method includes receiving input corresponding to aninteraction of the remove element. Interacting with the remove elementcauses the summary to be removed from the graphical interface thatdisplays the other summaries of security events. Thecomputer-implemented method includes updating the graphical interface toremove the summary from the graphical interface that displays the othersummaries of security events.

In another particular embodiment, a system is provided that includes oneor more data processors and a non-transitory computer readable storagemedium containing instructions which when executed on the one or moredata processors, cause the processor to perform operations includingreceiving raw data and indexing the raw data. Indexing includes dividingthe raw data into time stamped searchable events that includeinformation relating to computer or network security. The operationsinclude storing the indexed data in an indexed data store. Theoperations include extracting one or more values from a field in theindexed data using a schema. The operations include searching the one ormore extracted field values for the security information. The operationsinclude determining a group of security events. The group of securityevents is determined using the security information. Each security eventof the group of security events includes a field value specified by acriteria. The operations include presenting a graphical interfaceincluding a summary of the group of security events, other summaries ofsecurity events, and a remove element. The remove element is associatedwith the summary. The operations include receiving input correspondingto an interaction of the remove element. Interacting with the removeelement causes the summary to be removed from the graphical interfacethat displays the other summaries of security events. The operationsinclude updating the graphical interface to remove the summary from thegraphical interface that displays the other summaries of securityevents.

In yet another particular embodiment, a computer-program product isprovided that is tangibly embodied in a non-transitory machine-readablestorage medium that includes instructions configured to cause one ormore data processors to receive, on a computing device, raw data andindexing the raw data. Indexing includes dividing the raw data into timestamped searchable events that include information relating to computeror network security. The instructions are further configured to causethe one or more data processors to store the indexed data in an indexeddata store. The instructions are further configured to cause the one ormore data processors to extract one or more values from a field in theindexed data using a schema. The instructions are further configured tocause the one or more data processors to search the one or moreextracted field values for the security information. The instructionsare further configured to cause the one or more data processors todetermine a group of security events. The group of security events isdetermined using the security information. Each security event of thegroup of security events includes a field value specified by a criteria.The instructions are further configured to cause the one or more dataprocessors to present a graphical interface including a summary of thegroup of security events, other summaries of security events, and aremove element. The remove element is associated with the summary. Theinstructions are further configured to cause the one or more dataprocessors to receive input corresponding to an interaction of theremove element. Interacting with the remove element causes the summaryto be removed from the graphical interface that displays the othersummaries of security events. The instructions are further configured tocause the one or more data processors to update the graphical interfaceto remove the summary from the graphical interface that displays theother summaries of security events.

In yet another particular embodiment, a computer-implemented methodincludes receiving, on a computing device, machine data. Thecomputer-implemented method further includes producing a summary of agroup of security events. The security events are derived from machinedata and are of a type used in a security information and eventmanagement field to analyze security issues. Producing the summarycomprises discarding event information using a data reduction model. Thecomputer-implemented method includes presenting a graphical interfaceincluding the summary of the group of security events, other summariesof security events, and a remove element. The remove element isassociated with the summary. The computer-implemented method includesreceiving input corresponding to an interaction of the remove element.Interacting with the remove element causes the summary to be removedfrom the graphical interface that displays the other summaries ofsecurity events. The computer-implemented method includes updating thegraphical interface to remove the summary from the graphical interfacethat displays the other summaries of security events.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,aspects, and advantages of the invention will become apparent from thedescription, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described in conjunction with the appendedfigures:

FIG. 1 is a block diagram illustrating components of an exemplarysecurity event management environment in which various embodiments ofthe present invention may be implemented;

FIG. 2 shows a block diagram of an embodiment of a security monitoringsystem;

FIG. 3 shows a block diagram of an embodiment of a data managementsystem;

FIG. 4 shows a diagram illustrating an embodiment of a graphicalinterface presented by a security monitoring system;

FIG. 5 shows a diagram illustrating an embodiment of a graphicalinterface presented by a security monitoring system;

FIG. 6 shows a diagram illustrating an embodiment of a display presentedby a security monitoring system.

FIG. 7 shows a diagram illustrating an embodiment of a graphicalinterface presented by a security monitoring system;

FIG. 8 shows a diagram illustrating an embodiment of a graphicalinterface presented by a security monitoring system;

FIG. 9 shows a diagram illustrating an embodiment of a graphicalinterface presented by a security monitoring system;

FIG. 10 shows a diagram illustrating an embodiment of a displaypresented by a security monitoring system;

FIG. 11 shows a diagram illustrating an embodiment of a displaypresented by a security monitoring system;

FIG. 12 illustrates a flowchart of an embodiment of a process performedby a data management system;

FIG. 13 illustrates a flowchart of an embodiment of a process performedby a security monitoring system; and

FIG. 14 illustrates a flowchart of an embodiment of a process performedby a security monitoring system.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiment(s) onlyand is not intended to limit the scope, applicability or configurationof the disclosure. Rather, the ensuing description of the preferredexemplary embodiment(s) will provide those skilled in the art with anenabling description for implementing a preferred exemplary embodiment.It is understood that various changes can be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims.

Referring first to FIG. 1, a block diagram illustrating an embodiment ofa security event management environment 100 is shown. Those of skillwill appreciate that other embodiments of the invention include systemshaving architecture varying from precisely that which is shown inFIG. 1. In a particular embodiment, the security event managementenvironment 100 may be included in a security information and eventmanagement (SIEM) system. In other embodiments, the security eventmanagement environment 100 may include or implement a security eventmanagement (SEM) system.

The system 100 includes one or more devices, such as a client device 110and a user device 120 operated by a client 105 and a user 115,respectively. The client 105 and/or the user 115 can interact with asecurity monitoring system 150 via a network 140 using respectivedevices 110 and/or 120. In at least one embodiment, the network 140, mayinclude a local area network (LAN), a wide area network (WAN), awireless network, and the like.

In addition to the components described here, the security monitoringsystem 150 may include or be implemented in a computing system. Thecomputing system may include conventional components such as aprocessor, an operating system, and volatile and non-volatile memory.Although depicted as a single computing system, the security monitoringsystem 150 may also be implemented as a network of computer systemsand/or processors. For example, the security monitoring system 150 mayinclude one or more service devices, such as servers, mainframecomputers, networked computers, any processor-based computing device,and similar types of systems and devices. In one embodiment, thesecurity management system includes a random access memory (RAM) coupledto a processor. The processor executes computer-executable programinstructions stored in memory. Such processors may include amicroprocessor, an ASIC, state machines, or other processors, and can beany of a number or arrangement of suitable computing processors. Suchprocessors include, or may be in communication with, code modules (orengines) and/or applications, which store instructions that, whenexecuted by a processor, cause the processor to perform the operationsdescribed herein. For example, the security monitoring system 150 mayinclude a data management system 152 and a security event filteringsystem 154, which are described in further detail below with respect toFIGS. 2-14. Some embodiments of the system have different and/or othermodules than the ones described herein. Similarly, the steps describedherein can be distributed among the modules in accordance with otherembodiments in a different manner than is described here.

Client device 110 and/or user device 120 can each be a single electronicdevice, such as a hand-held electronic device (e.g., a smartphone). Itwill be understood that client device 110 and/or user device 120 canalso include a system that includes multiple devices and/or components.The device(s) 110 and/or 120 can comprise a computer, such as thedesktop computer, a laptop computer or a tablet. In some instances, aparty 105 and/or 115 uses different devices at different times tointeract with security monitoring system 150. In one embodiment, thedevices 110 and/or 120 may be include any type of processor-basedplatform that operates on any suitable operating system that are capableof executing one or more code modules, engines, and/or applications,which store instructions that, when executed by a processor, cause theprocessor to perform the operations described herein.

The security monitoring system 150 provides the client 105 and/or theuser 115 with tools to manage security events in a security eventmanagement system, such as the system 100. Specifically, the securitymonitoring system 150 can collect data including raw data (e.g., machinedata, unstructured data, and/or weblogs) from one or more resources 160(e.g., resource 160-1 through resource 160-n), process the data (e.g.,internally and/or using one or more resources) to index the raw datainto time stamped events that are searchable, extract values from fieldsin the indexed raw data, filter security-related events from the indexedraw data to identify groups of events based on criteria, and/or presenta summary of groups of the filtered security events in a display view. Aresource 160 from which data is collected can include one or morecomputing devices, e.g., a server, a router, network devices, and/or auser device 120. The events can pertain to an activity occurring in thesystem 100, such as a computer action, access control, endpointactivity, a communication (sent or received over a network), and/ornetwork activity (e.g., network requests, connection attempts, trafficvia a network device (e.g., a firewall, a router, a switch, or anetwork), requests for proxy or HTTP data, or creation of new domains).

Events related to computer and network security may be presented asgroups of security events, where each group of security events have afield value that satisfies a criteria for the group of security events.A group of security events may be presented in or as part of a summarythat presents information summarizing the security events in the groupof security events. The summary may present one or more field valuesthat satisfies the criteria used to determine the group. With a summaryof a group of security events, one or more interactive elements may bepresented that further enable selective filtering of the summary (andthe group of security events). Selective filtering may enable thesummary to be removed based on interaction with an interactive elementby a user when the user determines the summary does not contain securityevents that are not relevant. Selectively filtering may also enable thesummary to be modified by changing a visual appearance of the summarybased on interaction with a control by a user when the user determinesthat the summary contains security events of interest (e.g., events thatrequire further investigation).

The system includes one or more display devices, such as display device170, display device 180, and display device 190. The display devices170, 180, 190 enable presentation of information in the securitymanagement system for monitoring security events. The display devices170, 180, 190 may present information via a graphical interface 172, agraphical interface 182, and a graphical interface 192, respectively.The graphical interfaces 172, 182, 192 may be generated by any componentin the system, such as the security monitoring system 150, the clientdevice 110, and the user device 120. The graphical interfaces 172, 182,192 may be included in embodiments illustrated and described in furtherdetail with respect to at least FIGS. 2-11. It may be appreciated thatelements described or shown herein the graphical interfaces 172, 182,192 are for purposes of example and that fewer elements, more elements,or different graphical interface elements may be used in implementationsof embodiments of the invention without departing from the underlyingconcepts of the invention.

Note that a graphical interface depicted in the figures may represent aweb-page that is presented to a user, with the graphical interfaceincluding one or more interactive elements (such as radio buttons,drop-down menus, interactive elements, selectable controls, data entryfields) that may be selected and/or activated by a user. The display ofthe graphical interface may result from any suitable method, includingthe execution of code or instructions, interpretation of markuplanguage, etc. by a processing element (such as a browser or otherapplication, computer, microprocessor, central processing unit, etc.).Further, the response to (or processing of) the selection or activationof a graphical interface element may be the result of the execution ofcode or instructions, interpretation of markup language, etc. by aprocessing element (such as a browser or other application, computer,microprocessor, central processing unit, etc.). Thus, in someembodiments a method, process, function, or operation may be implementedas a result of the execution of code or a set of instructions by asuitably programmed processor or computing device.

Note that each of the figures depicting the graphical interface andassociated elements may be associated with a software-implementedprocess or method that is implemented by a suitably programmed processoror computing device in order to: (a) generate one or more of thedepicted graphical interface elements; (b) permit a user to interactwith one or more of the graphical interface elements (such as byactivating an element or entering data into a data field); (c) process auser's selection or activation of a graphical interface element, orentry of data into a data field; or (d) perform one or more processes,operations or functions associated with the inventive service.

As detailed further below, the client 105 and/or the user 115 caninteract with the security monitoring system 150 via a graphicalinterface 172, 182, 192 to dynamically filter events, such asnetwork-type activities, that are identified as being potentiallyrelated to a security threat. Therefore, a client (e.g., the client 105)and/or a user (e.g., the user 115) has the ability provided by thesecurity management system 100 to reduce time to investigate securityevents, such as those related to network activity, by using his/her ownexperience and knowledge to identify the most concerning events.

Now referring to FIG. 2, a block diagram of an embodiment of a securitymonitoring system 200 is shown. The security monitoring system 200 maybe included or implemented in the security monitoring system 150 ofFIG. 1. The security monitoring system 150 can be, in part or in itsentirety, in a cloud. In some instances, at least part of securitymonitoring system 150 is present on a device, such as a client device110. In some instances, various components in security monitoring system150 are present in one or more resources. For example, the datamanagement system 152 may be stored on or operated from the resource160-1, and the security event filtering system 232 may be stored on andoperated from the resource 160-2. Thus, security monitoring system 150can include a distributed system.

A data collector 205 collects data, such as raw data, from one or moreresources 160. can include unstructured data, structured data, and/ormachine data. The data can include data from web logs and/or can pertainto web access. The data can pertain to network-based activities.Discrete events can be present within the data. These events can includeHTTP requests and/or traffic logs. The events can pertain to an activityoccurring in the system 200 such as a such as a computer action, accesscontrol activity, endpoint activity, a communication (sent or receivedover a network), and/or network activity (e.g., network requests,connection attempts, traffic via a network device (e.g., a firewall, arouter, a switch, or a network), requests for proxy or HTTP data, orcreation of new domains). As will be described in further detail herein,the collected data can be segmented into the events (e.g., time-basedevents) and particular values can then be extracted from the events.

Initially, and as further detailed below, a field extractor 210 extractsa timestamp from each event. Based on the timestamp, data collector 205stores each event in an appropriate index in an event data store 215.The collected data corresponding to a time-based event may indicate atime-stamp of an event. The collected data may include indicate a hostdevice associated with the event and a source of the event. The hostdevice associated with the event may correspond to a machine (or hostdevice) from which the event originated. The source of the event mayindicate source information, such as a source from where the collecteddata came. The source information may indicate a type of the source,which corresponds to a type of the collected data. The event data store215 may include an indexed data store (e.g., a time-series data store)that stores each event based on indexed data corresponding to timestampsextracted from the events. The time stamped stored events may includeinformation related to computer security or network security.

A search engine 220 can then locate events pertinent to a particularanalysis at hand. A search engine 220 can access and search all or partof the event data store 215. Events corresponding to a particular timeperiod may be retrieved based on events having a time-stamp within theparticular time period. The search may include, e.g., a request toreturn all events or identifiers of all events having a value for afield meeting a criterion. A search may originate from a client via agraphical interface or may be received via a display interface engine225. For example, filter engine 230 may request the search engine 220 toproduct time-based events for a particular time period. Events with timestamps within the particular time period can then be retrieved by searchengine 220 from event data store 215. Data collector 205, fieldextractor 210, event data store 215 and search engine 220 can be part ofa data management system 222, described in further detail in referenceto FIG. 3 below. The data management system 222 may include or may beimplemented as the data management system 152 of FIG. 1.

Additionally, in a request to the search engine 220, the filter engine230 may specify values for one or more fields used to filter thetime-based events to locate events having particular type of information(e.g., computer or network security). The events may be identified basedfields having information related to computing activity such as accesscontrol information (e.g., login, logout, access allowed, accessfailure, or use of default accounts), endpoint information (e.g.,malware infections, system configuration, system state, patch status, ortime synchronization), and/or network traffic information (e.g., networkrequests, connection attempts, traffic via a network device, requestsfor proxy or HTTP data, HTTP requests, or creation of new domains). Thesearch engine 220 may search indexed data of time stamped events forparticular fields specified in a search request.

The filter engine 230 may provide an event aggregator engine 235 withtime stamped events that have been identified as having informationrelated to computer or network security based on criterion specified bythe filter engine 230. Based on the events received from the filterengine 230, the event aggregator engine 235 may determine events a groupof the events. In a particular embodiment, the event aggregator engine235 may determine the group of events corresponding to a particular timeperiod based on identifying events that have a time-stamp within theparticular time period. The event aggregator engine 235 may furtherdetermine the group of events using the information that was used tolocate the events filtered by the filter engine 230. In a particularembodiment, the event aggregator engine 235 may group the events basedon events having one or more field values that relate to securityinformation. In this embodiment, the field values of the events may beexamined to determine whether they are included in or satisfy a criteriadefining such a group.

In a particular embodiment, the event aggregator engine 235 maydetermine a group of security events based on the time stamped eventsprovided by the filter engine 230. The time stamped events may befiltered by the filter engine 230 based on security informationassociated with criteria specified by the event aggregator engine 235.Following the event aggregator engine's 235 determination as to whichvalues are to be examined for the time stamped events provided by thefilter engine 230, the field extractor 210 may extract the appropriatevalues and return them to event aggregator engine 235. The eventaggregator engine 235 may perform one or more correlation searches ofthe time stamped searchable events using the one or more extractedvalues. A correlation search may be performed of the extracted valuesbased on the criteria. The group of security events may be determinedbased on results of the correlation search.

The criteria used to identify events of interest may be based on one ormore fields of one or more time stamped events, such as a value or arange of values. Examples of criteria used to determine a group ofsecurity events are described and illustrated with respect to FIGS. 4,5, and 7-9. To identify the events having field values that relate tosecurity information, the event aggregator engine 235 may determinevalues to extract from the events using the security information. Eventsthat have one or more fields specified by a criteria (e.g., a criteriafor a potential security threat) may be added to the group of events. Agroup of events defined by a particular criteria may be useful foridentifying patterns of events that occur in a similar manner or thatare related in some way suggesting a potential security threat.

The display interface engine 225 is responsible for providing aninterface that presents information determined by the security eventfiltering system 232 to a client or a user. The display interface engine225 may present a graphical interface (e.g., the graphical interface172, the graphical interface 182, or the graphical interface 192) to adisplay device (e.g., the display device 170, the display device 180, orthe display device 190) coupled to the security monitoring system 200.In a particular embodiment the display interface engine 235 maydetermine a summary of one or more groups of security-related eventsdetermined by the event aggregator engine 235. One or more of thesesummaries presented in the graphical interface may be presented by thedisplay interface engine 225.

A summary may include information that summarizes one or more fieldsincluded in one or more security events of the group of security events.Such summary information may include information such as a count of thenumber of events in the group of security events and/or a metricsummarizing a particular field in each event of the group of securityevents. The summary may include one or more fields determined based on afield in one or more security events of the group. The summary may bebased on results of one or more correlation searches performed by theeven aggregator engine 235. In a particular embodiment, the summary of agroup of security events and/or the underlying group of security eventsassociated with the summary may be stored in a database for retrieval ata later time. Storage of the summary may include storing data associatedwith one or more of the security events in the group of security eventscorresponding to the summary.

In particular embodiments, the summary may be an interactive element ormay include one or more interactive elements (e.g., selectablecontrols). Interaction with the summary or one or more interactiveelements may cause information related to one or more security events ofthe group of security events to be displayed in the graphical interface.When information related to the security events is displayed in thegraphical interface, interaction with the summary may cause the securityevents to be hidden from display in or removed from the graphicalinterface. The information related to the one or more security eventsmay be displayed with the summary in the graphical interface. Additionaldetails and examples of a summary of security events shall be describedin further detail with respect to FIGS. 4-6 and FIGS. 7-9. Providing asummary of security events affords a user an ability to improveunderstanding of relationships between security events. A summaryenables the user to decrease effort involved for identification andisolation of events by blacklisting and/or whitelisting groups ofsecurity-related events.

In particular embodiments, the interface may provide additionalinformation about a summary of a group of security events and/or each ofthe security events in the summary. The additional information mayinclude charts, visual displays, graphs, statistics, metrics, or otherdisplays of related information, or a combination thereof, associatedwith the summary and/or based on information from data associated withthe group of security events of the summary.

In particular embodiments, the security event filtering system 232 mayroutinely, periodically, automatically, or dynamically modify thegraphical interface for events identified by the data management system222 based on new raw data collected by the data collector 205. Forexample, the display interface engine 225 may update the graphicalinterface to update a summary of a group of security events based on newsecurity events. The new security events may be identified by the eventaggregator engine 235 as belonging to the group of security events afterthe graphical interface had been generated. Further, the additionalinformation displayed in the graphical interface may be updated ormodified accordingly based on a modification to a summary of a group ofevents displayed in the graphical interface.

To reduce time needed by a user to sorting through security events forpotential security events of interest, the graphical interface mayinclude one or more features to enable selective filtering of at leastone summary of a group of security events displayed in the graphicalinterface. In a particular embodiment, the graphical interface mayinclude one or more interactive elements that enable selective filteringof a summary of a group of security events.

For example, the graphical interface may include an interactive element(e.g., a remove element) that, when interacted with, causes a summary ofa group of security events associated with the interactive element to beremoved (“whitelisted”) from the graphical interface. This featureenables the user to remove security events that may are acceptable(e.g., not relevant for identification of a particular security threat).

In another example, the graphical interface may include an interactiveelement (e.g., a modify element) that, when interacted with, causes asummary of a group of security events associated with the interactiveelement to be modified in the graphical interface. In other words, thesummary may be “blacklisted” by being modified to identify asignificance of the security events in the group shown for the summary.In a particular embodiment, modification of the summary may includechanging a visual appearance of the summary in the graphical interface.Changing the visual appearance of the summary may include highlightingthe summary, changing a color of the summary, or any other change thataffects how the summary appears in the graphical interface. For example,the summary may be displayed in a different position or location in thegraphical interface.

In a particular embodiment, the display interface engine 225 maygenerate one or more views or displays (e.g., a filter panel) thatinclude information associated with at least one summary of a group ofsecurity events that was selectively filtered (e.g., blacklisted orwhitelisted) from the graphical interface. In particular embodiments, adisplay may include information associated with at least one blacklistedsummary and/or at least one whitelisted summary. The display may includeone or more interactive elements associated with each of the summariesdisplayed in the display. Interaction with one of the interactiveelements associated with a summary in the view may enable a user to undoan action that caused the summary to be included in the display. Forexample, selection of an interactive element associated with a summarythat is whitelisted may cause the summary to be added back to thegraphical interface that displaying summaries before selective filteringwas applied. In another example, selection of an interactive elementassociated with a summary that is blacklisted may cause modification ofthe summary on the graphical interface to be undone.

In a particular embodiment, the graphical interface may provide one ormore interactive elements that, to selectively suppress a summary for aperiod of time. The display interface engine 225 may generate a displayor a view (e.g., a suppression panel), or alternatively modify thegraphical interface to enables a user to specify a current or futuretime, or time period when the summary is to be suppressed, or removedfrom the display. The display interface engine 225 may remove thesummary from the graphical interface for time period specified via thesuppression panel.

While “event” has been described as a time stamped, searchable segmentof raw data (e.g., unstructured data, machine data, and/or weblogs) in adata store (e.g., a time series data store), an “event” in alternativeembodiments may include any kind of security-related informationtypically referred to as an “event” in a SIEM field, and such events maybe derived from raw data. Such “events” need not be limited to timestamped, searchable segments of raw data. Vendors in a SIEM field mayimplement a process to segment data based on a “data reduction model”whereby events are discarded except events recognized as notable. Inalternative embodiments, one or more summaries displayed in a graphicalinterface as described herein may include one or more summaries of SIEMevents that are obtained from data based on application of a datareduction model. A summary of SIEM events may be selectively filtered(e.g., blacklisted and/or whitelisted) with respect to a summary in agraphical interface. The summary of SIEM events may include featuressuch as one or more interactive elements associated with the summary.

Thus, security monitoring system 150, 200 can reduce an amount of eventspresented for analysis to a user by providing a system that organizesand correlates related events. The system further provides tools to foridentification and analysis of security events that may be related to apotential threat by a particular mechanism or source. These features canbe particularly advantageous in the security field, where securitythreats evolve in technique and style.

The embodiments described with respect to FIG. 2 and other embodimentsand examples of functions and features of the security event filteringsystem 232 are described in further detail and illustrated with respectwith FIGS. 4-11.

FIG. 3 shows a block diagram of an embodiment of a data managementsystem 222. The data management system 222 may include or be implementedwithin the data management system 152 of FIG. 1. The data intake 305receives data, e.g., from a data provider, client, or user. The data caninclude automatically collected data, data uploaded by users, or dataprovided by the data provider directly. In some instances, the dataincludes a structure that allows for individual events and field valueswithin the events to be easily identified. The structure can bepredefined and/or identified within the data. For example, variousstrings or characters can separate and/or identify fields. As anotherexample, field values can be arranged within a multi-dimensionalstructure, such as a table. In some instances, data partly or completelylacks an explicit structure. For example, in some instances, nostructure for the data is present when the data is received and insteadis generated later. The data may include a continuous data stream caninclude multiple events, each with multiple field values.

A schema engine 310 identifies an applicable schema that can be used toextract specific field values by imposing structure on data.Specifically, a schema can be “bound” to data, by breaking a data stream(e.g., a byte stream) into events and/or extracting field values, suchas a time stamp. Schema binding can occur while receiving data, prior tostoring data, while storing data, while processing data, whileretrieving data, while responding to a search query or some combinationof the above (e.g., separating data into events at intake and extractingfield values from events while responding to a search query). Latebinding schema can be used, which imposes structure on the data at querytime rather than at storage or ingestion time. Thus, the schema may beapplied at query time as opposed to an earlier stage when the data isbeing born (e.g., when the data is received).

Schema engine 310 can itself estimate a schema or can determine a schemabased on input from a client or data provider. The input can include theentire schema or restrictions or identifications that can be used toestimate or determine a full schema. Such input can be received toidentify a schema for use either with structured or unstructured dataand can be used to reliably extract field values. The schema can beestimated based on patterns in the data (e.g., patterns of characters orbreaks in the data) or headers or tags identifying various fields in thedata, such as <event><message time>2014.0I.05.06.59.59</> . . . </>).Schema can be received or estimated in a variety times, including (insome instances) any time between receipt or indexing of the data and aquery time. The time that the schema is actually received or estimatedwithin the receipt-to-indexing time period may be determined based on asetting or system load. Schema engine 310 can perform the schemaestimation once or multiple times (e.g., continuously or at routineintervals). Once a schema is determined, it can be modified (e.g.,periodically, at regular times or intervals) upon receivingmodification-requesting input, upon detecting a new or changed patternin the input, or upon detecting suspicious extracted field values (e.g.,being of an inconsistent data type, such as strings instead ofpreviously extracted integers). In some instances, a client or dataprovider can provide input indicating a satisfaction with or correctionto estimated schema. Received or estimated schemas are stored in aschema data store 315

Using the schema, an event parser 320 can separate the received datainto events. For example, event parser 320 can separate data betweenparticular start and stop tags, or separate data within a table's row,or separate data within particular character numbers in the data. Alsousing the schema, a field extractor 325 can extract various fieldvalues. In some instances, field extractor 325 further attaches asemantic meaning to the extracted field values (e.g., based on a lengthand/or character types of the field values). Field extractor 325 canfurther convert field values into a particular (e.g., standard or easilysearchable) format.

It is noted that data collector 205 from system 200 can largely parallelthe combination of data intake 305 and event parser 320. While system200 does not explicitly show schema engine 310 and schema data store315, it will be appreciated that system 200 can include these elements,which can then be utilized by data collector 205 and field extractor210.

A storage engine 330 can store data in an event data store 335, whichcan correspond to event data store 215. It will be appreciated thatevent data store 335 can include multiple data stores or sub-datastores. Event data store 335 can be stored in working, short-term and/orlong-term memory. In various instances, event data store 335 can includeraw data, extracted events or extracted field values. It will beappreciated that, in some instances, part of the data received by dataintake 305 can be deleted or not stored (e.g., field breaks).

Events and/or field values can be stored at locations based on a fieldvalue. For example, a field value identifying a message sender may bestored in one of ten data stores, the data store being chosen based on amessage time. In some instances, rather than grouping various datacomponents at specific storage areas, event data store 335 includes anindex that tracks identifiers of events and/or fields and identifiers offield values. Thus, for example, the index can include an element for“Data type=“webpage request” (indicating that the element refers to afield value of “webpage request” for the field “data type”) and thenlist identifiers for events with the field value (e.g., “Events 3, 7, 9and 16”). Selective storage grouping can be referred to as storing datain “buckets”. Bucket definitions can be fixed or defined based on inputfrom a data provider, client or client. Input and/or automatic rules canbe used to add, merge or delete buckets.

In some instances, a time-series data store is used, such that eventsand/or field values are stored at locations based on a timestampextracted from the events. This can allow events with recent timestamps(e.g., which may have a higher likelihood of being accessed) to bestored at preferable memory locations that lend to quicker subsequentretrieval. Further, parallel processing can then be performed, with eachprocess operating on a different time bucket.

A search engine 340 (which can correspond to search engine 220) cansubsequently access and search all or part of event data store. Thesearch can be performed upon receiving a search query from a client,user or client, or the search can be performed periodically and/or atdefined intervals or times. Segregation of data into events and/orfields can allow for more efficient searching. The search may include,e.g., a request to return all events or identifiers of all events havinga value for a field meeting a criterion. To illustrate, search engine340 can retrieve all events having a timestamp within a defined timeperiod, and/or all events having a first field value (e.g., HTTP method)set to a specified value (e.g., GET).

The search may include, e.g., a request to return values for one or morefirst fields for all events having specified values (e.g., specificvalues or values within a specific range) for one or more second fields.To illustrate, search engine 340 can retrieve all URLs in events havinga timestamp within a defined time period, or all events having a firstfield value (e.g., HTTP method) set to a specified value (e.g., GET).

In some instances, upon retrieving the event data of interest, searchengine 340 may further process the results. The processing may beperformed based on an individual value (e.g., to obtain a length ordetermine if an extracted field value matches a specified value). Insome instances, processing can be performed across values, e.g., todetermine an average, frequency, count or other statistic. Search engine340 can return the search result to data provider, client or user, e.g.,via an interface (such as a web interface or app interface) or email.

Now turning to FIG. 4, a diagram illustrating an embodiment of agraphical interface 400 presented by a security monitoring system isshown. The graphical interface 400 may be presented by the securitymonitoring system 150 of FIG. 1 or the security monitoring system 200 ofFIG. 2. The graphical interface 400 is an example of a graphicalinterface that may be generated by the display interface engine 225 ofFIG. 2. As shown, the graphical interface 400 presents information aboutevents related to activity associated with computing and networksecurity. In FIG. 4, the time-based events may be based on raw dataincluding hypertext transfer protocol (HTTP) or proxy data.Specifically, the graphical interface 400 presents information aboutHTTP user agents identified in time stamped events obtained from rawdata.

In a particular embodiment, the graphical interface 400 may includeinformation about one or more groups of security events. The graphicalinterface 400 illustrates representative summaries including a summaryof a group of security events 410, a summary of a group of securityevents 420, and a summary of a group of security events 430. While therepresentative summaries 410, 420, 430 are discussed, the graphicalinterface 400 may also display other summaries of other groups of eventsdetermined by the security event filtering system 232. Each of thesummaries 410, 420, 430 may each include a group of security eventsdetermined by the security filtering system 232. In the embodimentillustrated in FIG. 4, each of the group of security events associatedwith summaries 410, 420, 430, respectively, has one or more fields, suchas a user agent string (e.g., “http_user_agent” field), specifying bycriteria to identify groups of events related to activity associatedwith particular HTTP user agent strings. To further illustrate, securityevents associated with the summary 410 may be group because the securityevents in the group have an HTTP user agent string with a particularlength (e.g., a length value of 44) that satisfy criteria indicating aparticular length or range of lengths for a HTTP user agent string. Thecriteria for a length based on a HTTP user agent string may be based ona length of particular misspelled or malicious user agent strings. Assuch, security events satisfying the criteria may be grouped andsummarized in the summary 410. The summary may enable a user to reduceeffort to identify events related to network activity with satisfyingthe criteria.

One or more of the summaries 410, 420, 430 may include informationsummarizing a group of security events in the respective summaries 410,420, 430. For example, the summary 410 may include a value of the field,such as the “http_user_agent” identifying a HTTP user agent field ineach of the group of security events that satisfy criteria for thegroup. The summary 410 may include other information based on commonfields or information that describes the group of security events. Forexample, the summary 410 may include a length of the http_user_agentstring that is common or that defines the events in the group ofsecurity events in the summary 410. The summary 410 may include a countof a number of security events in the group of security events includedin the summary 410. The summary 410 may include a time corresponding towhen the network activity associated with the security events occurred.Although not shown, the summaries 410, 420, 430 may include or implementan interactive element. Interaction with the interactive element maycause information related to the one or more security events of thegroup of security events of the respective summary 410, 420, 430 to bepresented in the graphical interface 400 with the respective summary410, 420, 430. Interaction with a summary 410, 420, 430 may causesecurity events displayed in the graphical interface 400 with thesummary 420, 420, 430 to be hidden from display or removed from thegraphical interface 400 when one or more security events are displayedwith the respective summary 410, 420, 430.

In a particular embodiment, one or more of the summaries 410, 420, 430may include one or more interactive elements to control selectivefiltering as enabled by security event filtering system 232 of FIG. 2.For example, a summary in the graphical interface 400 may include aremove element (“whitelist” control), a modify element (“blacklist”control), or both. The remove element may enable a user to remove(“whitelist”) the summary from the graphical interface 400. A user maydesire to remove the summary based on a determination that theinformation provided by the summary is acceptable, not warrantingfurther analysis. The modify element may enable a user to modify(“blacklist”) the summary in the graphical interface 400 to cause thegraphical interface 400 to change a visual appearance of the summary. Auser may desire to modify the summary based on a determination that thesecurity events associated with the summary require furtherinvestigation as a possible security threat.

The summary 410 illustrates an example with a remove element 440 and amodify element 450. Although not shown, a selection of the removeelement 440 may cause the summary 410 to be removed from the graphicalinterface 400. A selection of the modify element 450 may cause thesummary 410 to be modified in graphical interface 400. In someembodiments, the summary 410 may be modified to be displayed in adifferent position/location in the graphical interface 400, such as at atop of a list of the summaries. In other embodiments, the summary 410may be highlighted, or a visual appearance (e.g. a color) of the summary410 may be changed. Although an example is described for one summary ofthe graphical interface 400, any number of summaries may includeinteractive elements, such as the remove element 440 or the modifyelement 450.

In particular embodiments, the graphical interface 400 presentsadditional information based on the security events corresponding to thesummaries including the summaries 410, 420, 430. For example, theadditional information may include a minimum length corresponding to ashortest user agent string found in the data, a mean length representingan average length of a user agent string in the data, a maximum length:representing a longest user agent string found in the data, a standarddeviation of user agent strings found in the data, and a total count ofuser agent strings in the data. The graphical interface 400 may presenta chart illustrating information associated with each of the summaries.Such additional information may be useful for determining whether thesummaries 410, 420, 430 identify a security threat that requires furtheranalysis. The statistics may assist in the identification of a trendbetween summaries based on similar lengths of user agent strings. Theidentification may be useful for identifying security threats posed froma single source applying different mechanisms, such as different useragent strings.

Now turning to FIG. 5, a diagram illustrating an embodiment of agraphical interface 500 presented by a security monitoring system isshown. The graphical interface 500 may be presented by the securitymonitoring system 150 of FIG. 1 or the security monitoring system 200 ofFIG. 2. The graphical interface 500 is an example of a graphicalinterface that may be generated by the display interface engine 225 ofFIG. 2. As shown, the graphical interface 500 presents information aboutevents associated with network activity. In FIG. 5, the time-basedevents may be based on raw data including HTTP and proxy data.Specifically, the graphical interface 500 presents information aboutnetwork traffic data identified in time stamped events from the HTTP andproxy data.

The graphical interface 500 may include information about one or moregroups of security events, each event identified based on having a fieldspecified in a criteria of network security. The graphical interface 500illustrates representative summaries including a summary of a group ofsecurity events 520 and a summary of a group of security events 530.While the representative summaries are discussed, the graphicalinterface 500 may display other summaries of events. In the exampleillustrated in FIG. 5, each of the summaries 520 and 530 represent asingle security event determined by the security event filtering system232.

Each security event associated with one of the summary 520, 530,respectively, has one or more fields that satisfy criteria for activityassociated with network traffic security. For example, the eventsassociated with each of the summary 510, 520 includes a source field(e.g., “src” field) and a time field (e.g., “lastTime” field) which areused to satisfy criteria identifying network traffic from a particularsource during a particular time period. The criteria may be defined toidentify network traffic events where data was exchanged during aparticular time range, such as 12:00 am to 12:00 pm, from a particularsource. Such criteria may enable identification of an increase innetwork traffic activity during the particular time period suggestive ofa potential issue relating to network security. The security events thespecify the criteria may be grouped into individual summaries 520, 530because the security events are distinct events distinguishable by thesource field.

Each of the summaries 520, 530 may include information summarizing thesecurity event for the respective summaries 520, 530. For example, thesummary 520 may include a value of the source field (“src”) identifyinga source of the security event associated with the summary 520, thedestination field (“dest”) identifying a destination of the securityevent associated with the summary 520, a time field (“lastTime”)identifying a time the event occurred, and a byte field (“byte”)identifying the number of bytes indicated in the security eventassociated with the summary 520. The summary 520 may include a count ofa number of security events in the group of security events of thesummary 520. Although not shown, the summaries 520, 530 may include orimplement an interactive element. Interaction with the interactiveelement of a summary (e.g., the summary 520 or the summary 530) maycause the group of security events associated with the summary to beincluded in the graphical interface 500.

In a particular embodiment, the graphical interface may include one ormore interactive elements to control selective filtering (blacklistingand whitelisting) as enabled by the security filtering system 232. Forexample, the graphical interface 500 may include an interactive element510. Interaction with the interactive element 510 may cause the datainterface engine 235 to present a display (e.g., a “filter panel”), suchas a display shown in FIG. 6 described herein, that enables a user toremove (whitelist) the summaries 520, 530 in the graphical interface500. The display may include information describing information providedin the summaries 520, 530 and one or more interactive elements to enableselection of one or more of the summaries 520, 530 for filtering.Details of features and functions of the display presented in responseto selection of the interactive element 510 may be described in furtherdetail with respect to FIG. 6. Although not shown, the graphicalinterface 500 may include one or more interactive elements, such as amodify element and a remove element for selective filtering as describedwith respect to FIG. 4.

In particular embodiments, the graphical interface 500 presentsadditional information based on the security events corresponding to thesummaries including the summaries 520, 530. For example, the additionalinformation may include a minimum bytes representing a shortest bytelength found in the data, mean bytes representing an average byte lengthof a traffic event in the data, maximum bytes representing a longestbyte length found in the data, standard deviation (or variance from theaverage) of URL strings found in the, and a total count indicating atotal number of traffic events in the data. The graphical interface maypresent a chart displaying the minimum, average, and maximum bytes oftraffic as a line graph over time. These statistics may assist in theidentification of a trend of security events associated with networktraffic. For example, such information may be used to investigatetraffic data byte lengths to identify connections with a large bytecount per request, or a source making a high number of connectionattempts, but with small byte count sizes. Such information promotesidentification of malicious network activity (e.g., a security threat)that may be determined based on a number of requests from a particularsource to a particular destination and an amount of data requested.Using the interactive element, summaries may be whitelisted to focusinvestigation towards summaries that require further analysis.

In FIG. 6, a diagram illustrating an embodiment of a display 600presented by a security monitoring system is shown. The display 600(e.g., “filter panel”) may be presented by the security monitoringsystem 150 of FIG. 1 or the security monitoring system 200 of FIG. 2.Specifically, the display 600 may be generated and presented by thedisplay interface engine 225 of FIG. 2.

The display 600 may be presented in response to an interaction with aninteractive element (e.g., the interactive element 510 of FIG. 5, theinteractive element 710 of FIG. 7, the interactive element 810 of FIG.8, the interactive element 910 of FIG. 9) included in a graphicalinterface, such as one of the graphical interfaces 500, 700, 800, 900.For illustration, the display 600 is explained with respect to FIG. 5.The display 600 may include representative filter summary information610 and filter summary information 640 identifying a correspondingsummary from the graphical interface 500. The filter summary information610, 640 may include all or a portion of a respective summary 520, 530from the graphical interface 500. In a particular embodiment, each ofthe filter summary information 610, 640 may be associated with arepresentative interactive element 620 and a representative interactiveelement 630, respectively. The interactive element 620, 630 may controlwhitelisting or blacklisting of a respective summary in the graphicalinterface 500. In a particular embodiment, when the interactive element620, 630 is selected, a corresponding summary in the graphical interface500 may be removed (whitelisted), and when the interactive element 620,630 is not selected, the corresponding summary may be added to thegraphical interface 500. In another particular embodiment, when theinteractive element 620, 630 is selected, a corresponding summary in thegraphical interface 500 may be modified (blacklisted), and when theinteractive element 620, 630 is not selected, modification of thecorresponding summary may be undone. The modification may includechanging a visual appearance of the corresponding summary. In someembodiments, the display 600 may include an interactive element to causethe graphical interface 500 to be updated based on interaction with oneor more of the interactive elements 610, 640.

Now turning to FIG. 7, a diagram illustrating an embodiment of agraphical interface 700 presented by a security monitoring system isshown. The graphical interface 700 may be presented by the securitymonitoring system 150 of FIG. 1 or the security monitoring system 200 ofFIG. 2. The graphical interface 700 is an example of a graphicalinterface that may be generated by the display interface engine 225 ofFIG. 2. As shown, the graphical interface 700 presents information aboutevents associated with domain activity. Specifically, the graphicalinterface 700 presents information about domain activity identified intime stamped events.

The graphical interface 700 may include information about one or moregroups of security events, each event identified based on having a fieldspecified in a criteria for domain activity indicative of networksecurity. The graphical interface 700 illustrates representativesummaries including a summary of a group of security events 720 and asummary of a group of security events 730. While the representativesummaries 720, 730 are illustrated, the graphical interface 700 maydisplay other summaries of events. In the example illustrated in FIG. 7,each of the summaries 720 and 730 may be associated with a singlesecurity event determined by the event aggregator engine 235 for therespective summaries 720, 730. The security event associated with thesummary 720, 730, respectively, has one or more fields, such as a timefield (e.g., “lastTime” field), a destination field (e.g., “dest”field), and a count field (“count”) that satisfy criteria for activityassociated with network traffic data. The security event filteringsystem 232 may determine the security events identified for each of thesummaries 720, 730.

The may be identified based on satisfaction of criteria for identifyingnetwork traffic events including a particular range of values of a countof requests made for a particular destination during a particular timeperiod (e.g., 12:00 pm to 12:00 am). Such criteria may enableidentification of an increase in domain requests for a particulardestination during the particular time period suggestive of a potentialissue relating to network security. The security events that specify thecriteria may be grouped into individual summaries 720, 730 based onhaving distinct values for the destination field.

Each of the summaries 720, 730 may include information summarizing thesecurity event for the respective summaries 720, 730. For example, thesummary 720 may include a value of the “dest” field identifying adestination of the security event associated with the summary 720, a“lastTime” field identifying a time the event occurred, and the “byte”field identifying a count for requests for a particular domainassociated for the security event of the summary 720.

In a particular embodiment, the graphical interface may include one ormore interactive elements to control selective filtering as enabled bythe security filtering system 232. The selective filtering may enablewhitelisting or blacklisting of events. For example, the graphicalinterface 700 may include an interactive element 710. Selection of theinteractive element 710 may cause the security filtering system 232 topresent a display (e.g., a “filter panel”), such as a display shown inFIG. 6 described herein, that enables a user to remove (whitelist) ormodify (blacklist) the summaries 720, 730 in the graphical interface700. The display may include information describing the summaries 720,730 and one or more interactive elements to enable selection of one ormore of the summaries 720, 730 for filtering. Details of features andfunctions of the display presented in response to selection of theinteractive element 710 may be described in further detail with respectto FIG. 6. Although not shown, the graphical interface may include oneor more interactive elements, such as a modify element and a removeelement for selective filtering as described with respect to FIG. 4.

In particular embodiments, the graphical interface 700 presentsadditional information based on the security events corresponding to thesummaries including the summaries 720, 730. The graphical interface maypresent a chart displaying new domain activity based on a particularfield (e.g., time or top level domain name) associated with domainactivity. These statistics may assist in the identification of a trendof security events associated with domain activity. Further, the summaryof security events included in the graphical interface 700 may be usefulfor identification of a count of requests for a particular domain.

Now turning to FIG. 8, a diagram illustrating an embodiment of agraphical interface 800 presented by a security monitoring system isshown. The graphical interface 800 may be presented by the securitymonitoring system 150 of FIG. 1 or the security monitoring system 200 ofFIG. 2. The graphical interface 800 is an example of a graphicalinterface that may be generated by the display interface engine 225 ofFIG. 2. As shown, the graphical interface 800 presents information aboutevents associated with network traffic. Specifically, the graphicalinterface 800 presents information about HTTP activity identified intime stamped events.

The graphical interface 800 may include information about one or moregroups of security events, each event identified based on having a fieldspecified in a criteria for events related to HTTP activity indicativeof network security (e.g., unknown HTTP traffic). The graphicalinterface 800 illustrates representative summaries including a summaryof a group of security events 820 and a summary of a group of securityevents 830. While the representative summaries 820, 830 are illustrated,the graphical interface 800 may display other summaries of events. Inthe example illustrated in FIG. 8, each of the summaries 820 and 830 maybe associated with a group of security events determined by the securityevent filtering system 232 for the respective summaries 820, 830. Thegroup of security events associated with the summary 820, 830,respectively, has one or more fields, such as a count field (“count”)and a source field (“src”) that satisfy criteria for HTTP activity. Thesecurity event filtering system 232 may define the criteria determinethe security events identified for each of the summaries 820, 830 basedon satisfaction of criteria for identifying a particular number of HTTPrequests during a 24 hour time period. Such criteria may enableidentification of a sharp increase in HTTP requests from a particularsource during a time period, which may be suggestive of a potentialissue relating unknown HTTP requests. The security events that specifythe criteria may be grouped into individual summaries 820, 830 based onhaving distinct values for the destination field. Each of the summaries820, 830 may include information summarizing the security event for therespective summaries 820, 830.

In a particular embodiment, the graphical interface may include one ormore interactive elements to control selective filtering as enabled bythe security filtering system 232. The selective filtering may enablewhitelisting or blacklisting of events. For example, the graphicalinterface 800 may include an interactive element 810. Selection of theinteractive element 810 may cause the security filtering system 232 topresent a display (e.g., a “filter panel”), such as a display shown inFIG. 6 described herein, that enables a user to remove (whitelist) ormodify (blacklist) the summaries 820, 830 in the graphical interface800. Details of features and functions of the display presented inresponse to selection of the interactive element 810 may be described infurther detail with respect to FIG. 6. Although not shown, the graphicalinterface may include one or more interactive elements, such as a modifyelement and a remove element for selective filtering as described withrespect to FIG. 4. In the example illustrated in FIG. 8, the summaries820, 830 may include a filter field (“filter”) that identifies whetherthe summary 820, 830 has been blacklisted and/or whitelisted.

In particular embodiments, the graphical interface 800 presentsadditional information based on the security events corresponding to thesummaries including the summaries 820, 830. The graphical interface maypresent a chart displaying new HTTP activity as a function of a numberof HTTP requests and a source of the HTTP requests. These statistics mayassist in the identification of a trend of security events associatedwith HTTP activity. Further, the summary of security events included inthe graphical interface 800 may be useful for identification of a countof requests by a particular unidentified source.

Now turning to FIG. 9, a diagram illustrating an embodiment of agraphical interface 800 presented by a security monitoring system isshown. The graphical interface 900 may be presented by the securitymonitoring system 150 of FIG. 1 or the security monitoring system 200 ofFIG. 2. The graphical interface 900 is an example of a graphicalinterface that may be generated by the display interface engine 225 ofFIG. 2. As shown, the graphical interface 900 presents information aboutevents associated with network traffic. Specifically, the graphicalinterface 900 presents information about URL strings identified in timestamped events.

The graphical interface 900 may include information about one or moregroups of security events, each event identified based on having a fieldspecified in a criteria for events related to URL strings indicative ofnetwork security (e.g., malicious URL string). The graphical interface900 illustrates representative summaries including a summary of a groupof security events 920 and a summary of a group of security events 930.While the representative summaries 920, 930 are illustrated, thegraphical interface 900 may display other summaries of events. In theexample illustrated in FIG. 9, each of the summaries 920 and 930 may beassociated with a group of security events determined by the securityevent filtering system 232 for the respective summaries 920, 930. Thegroup of security events associated with the summary 920, 830,respectively, has one or more fields, such as a count field (“count”), auniform resource locator (URL) field (“url”), and a URL length field(“url length”) that satisfy criteria for analysis of URL strings. Thesecurity event filtering system 232 may define the criteria to determinethe security events identified for each of the summaries 920, 930. Thecriteria may be defined to identify a count of HTTP activity involvingURL strings with a particular length. Such criteria may enableidentification of a HTTP activity using a URL string that may containmalicious information as indicated by a length or a particular stringidentified in the URL. For example, the criteria may include a URLstring having a particular length because a URL string of a particularlength may suggest that the URL string contains an embedded SQL command(e.g., an SQL command for SQL injections), cross-site scripting (XSS),embedded command and control (C&C) instructions, or other maliciouscontent. The security events that specify the criteria may be groupedinto individual summaries 920, 930 based on having distinct values forthe destination field. Each of the summaries 920, 930 may includeinformation summarizing the security event for the respective summaries920, 930.

In a particular embodiment, the graphical interface 900 may include oneor more interactive elements to control selective filtering as enabledby the security filtering system 232. The selective filtering may enablewhitelisting or blacklisting of events. For example, the graphicalinterface 900 may include an interactive element 910. Selection of theinteractive element 910 may cause the security filtering system 232 topresent a display (e.g., a “filter panel”), such as a display shown inFIG. 6 described herein, that enables a user to remove (whitelist) ormodify (blacklist) the summaries 920, 930 in the graphical interface900. Details of features and functions of the display presented inresponse to selection of the interactive element 810 may be described infurther detail with respect to FIG. 6. Although not shown, the graphicalinterface may include one or more interactive elements, such as a modifyelement and a remove element for selective filtering as described withrespect to FIG. 4.

In particular embodiments, the graphical interface 900 presentsadditional information based on the security events corresponding to thesummaries including the summaries 920, 930. The graphical interface maypresent a chart displaying activity over a period of time correspondingto a particular length of a URL string. These statistics may assist inthe identification of a trend of security events associated with HTTPrequests for URL strings have a particular length suggestive ofmalicious activity. Further, the summary of security events included inthe graphical interface 900 may be useful for identification of activityusing a particular length URL string during a particular time.

FIG. 10 shows a diagram illustrating an embodiment of a display 1000presented by a security monitoring system. The display 1000 (e.g.,“filter panel”) may be presented by the security monitoring system 150of FIG. 1 or the security monitoring system 200 of FIG. 2. Specifically,the display 1000 may be generated and presented by the display interfaceengine 225 of FIG. 2.

The display 1000 enables a user to manage summaries that have beenremoved (whitelisted) from a graphical interface that displays thesummaries, such as one or more of the graphical interfaces 400, 500,700, 800, 900. In particular embodiments, a graphical interfacedisplaying a summary of security events may include an interactiveelement that causes the display 1000 to be presented. To illustrate, thedisplay 1000 presents a summary of a group of security events 1010 thathas been removed from the graphical interface, such as the graphicalinterface 500. The summary 1010 may display all or a portion of acorresponding summary presented in the graphical interface 500. Thesummary 1010 may be associated with an interactive element 1020 (e.g., aselectable control) that when interacted with presents one or moreoptions for managing the summary 1010. For example, the interactiveelement 1020 may include an option to add the summary 1010(“unwhitelist”) the summary by adding it back to the graphical interface500. In particular embodiments, the display 1000 may include additionalinteractive elements such as an interactive element 1030 and interactiveelement 1040. Interactive element 1030 may enable a user to confirm(e.g., save) an interaction on the interactive element 1020. In responseto interaction with the interactive element 1030, the display interfaceengine 235 may cause the summary 1020 to be added back to the graphicalinterface 500. The interactive element 1040 may enable a user to cancelinteraction with the interactive element 1020.

The panel 1000 is particularly useful as it enables a user to identifysummaries that have been whitelisted, which may otherwise be forgottenonce removed from a graphical interface. In an environment where thegraphical interface presents many summaries, a user may forget ormistakenly remove one or more summaries. The display 1000 enables theuser to undo what was whitelisted before. In some cases, a user maydesire to undo a whitelisted summary after further determination thatthe whitelisted summary may pose a security threat.

FIG. 11 shows a diagram illustrating an embodiment of a display 1100presented by a security monitoring system. The display 1100 (e.g.,“filter panel”) may be presented by the security monitoring system 150of FIG. 1 or the security monitoring system 200 of FIG. 2. Specifically,the display 1100 may be generated and presented by the display interfaceengine 225 of FIG. 2.

The display 1100 enables a user to manage summaries that have beenremoved (whitelisted) and/or summaries that have been modified(blacklisted) from a graphical interface that displays the summaries,such as shown in particular embodiments of graphical interfaces 400,500, 700, 800, 900. In particular embodiments, a graphical interfacedisplaying a summary of a group of security events may include aninteractive element that causes the display 1100 to be presented. Toillustrate, the display 1100 presents a summary of a group of securityevents 1110 that has been modified (blacklisted) from a graphicalinterface, such as the graphical interface 500. The summary 1110 maydisplay all or a portion of a corresponding summary presented in thegraphical interface 500. The display may additionally, or in thealternative, present a summary of a group of security events 1150 thathas been removed (whitelisted) from a graphical interface, such as thegraphical interface 500. The summary 1150 may display all or a portionof a corresponding summary presented in the graphical interface 500.

The summary 1110 and/or the summary 1150 may include or may beassociated with one or more interactive elements, such as arepresentative interactive element 1120 (e.g., a selectable control).The interactive element 1120 may include one or more options formanaging the summary 1110 and/or the summary 1150. For example, theinteractive element 1120 include an include an option to remove thesummary 1110 from the display 1000, which causes modification of thesummary in the graphical interface 500 to be undone. In another example,the interactive element 1120 may include an option to remove the summary1150 from the display, which causes the summary 1150 to be added back tothe graphical interface 500.

In particular embodiments, the display 1100 may include additionalinteractive elements such as an interactive element 1130 and interactiveelement 1140. Interactive element 1130 may enable a user to confirm(e.g., save) an interaction on the interactive element 1120. In responseto interaction with the interactive element 1130, the display interfaceengine 235 may cause the summary 1120 to be added back to the graphicalinterface 500. The interactive element 1140 may enable a user to cancelinteraction with the interactive element 1120.

The panel 1100 enables a user to identify summaries that have beenwhitelisted and/or blacklisted. Using the panel 1100, a user to change adecision made for whitelisting or blacklisting a summary in the eventthat further investigation of the summary 1110 or the summary 1150changes.

FIG. 12 illustrates a flowchart of an embodiment of a process 1200performed by a data management system. For example, the process 1200 maybe performed by the data management system 222 of FIG. 2 and/or the datamanagement system 300 of FIG. 3.

Process 1200 begins at block 1205, where data intake 305 receives data.Schema engine 310 identifies an applicable schema at block 1210. Eventparser 320 applies the schema to separate the data into events at block1215. Field extractor 325 applies the schema to extract field valuesfrom the events at block 1220. Storage engine 330 stores raw data,events and/or field values in event data store 335 (e.g., by assigningthe data, events and/or field values to buckets based on particularfield values) at block 1225.

Search engine 340 receives a search query from a searcher (e.g., clientor user) at block 1230. The search query can include one or morecriteria which can specify or constrain field values. Search engine 340searches event data store 335 at block 1235. The search can entailsearching only some of event data store 335 (e.g., that include fieldvalues of interest, such as information indicative of a securitythreat). The search can produce identifiers of events of interest.Search engine 340 may then collect other field values for those eventsof interest. A search result can include the collected other fieldvalues and/or a processed version thereof. Search engine 340 returns thesearch result to the searcher at block 1240.

It will be appreciated that the data management system 222 of FIG. 2,the data management system 300 of FIG. 3, and/or the process 1200 may bemodified such that schema is not bound to data (or only a portion of theschema is bound to data) immediately following intake. For example,schema could instead be bound to prior to storage of the data, duringstorage of the data, or at a query time (e.g., subsequent to block 1230of process 1200). Splunk Enterprise produced by Splunk Inc. of SanFrancisco is an exemplary system for creating a time series data storeusing a late binding schema. For example, Splunk Enterprise creates atime series data store by segmenting received raw data into events,extracting timestamps from each event, and storing each event in one ormore time series data stores that are searchable by timestamp (alongwith other metadata such as source, type, and the like). SplunkEnterprise allows later schema development of fields any time up toquery time.

The data management system 222, the data management system 300, and/orthe process 1200 can be modified to include features, featureconnections and/or flows as described in Carasso, David. ExploringSplunk Search Processing Language (SPL) Primer and Cookbook.

New York: CITO Research, 2012 and/or as described in Ledion Bitincka,Archana Ganapathi, Stephen Sorkin, and Steve Zhang. Optimizing dataanalysis with a semi-structured time series database. In SLAML, 2010.Each of these references is hereby incorporated by reference in itsentirety for all purposes.

FIG. 13 illustrates a flowchart of an embodiment of a process 1300performed by a security monitoring system. For example, the process 1300may be performed by the security monitoring system 150 of FIG. 1 and/orthe security monitoring system 200 of FIG. 2.

The process 1300 begins at block 1305, where raw data is received from adata store. The process continues to block 1310 where the raw data isindexed. The schema engine 310 performs indexing of the raw data whichmay include dividing the raw data into time stamped searchable events.The time stamped searchable events may include information relating tocomputer or network security. The security information correspond to oneor more fields in time stamped events. The one or more fields in thetime stamped events may include information related to computer ornetwork security. At block 1315, the schema engine 310 stores index data(based on indexing of the raw data) for each event in an appropriateindex in an event data store 215.

The process 1300 continues at block 1320, where one or more values areextracted from a field in the index data for each of the time stampedevents using a schema. The schema may be applied at query time. Anapplicable schema can be used to extract specific field values based ona structure imposed on the indexed data. The field extractor 325 mayextract one or more values from time stamped events indexed by theschema engine 310.

At block 1325, the process 1300 includes searching one or more extractedfield values (of the index data) for the security information. Forexample, the filtering engine 230 of FIG. 2 may request the searchengine 220 of FIG. 2 to search the one or more values extracted from afield of the index data for the security information.

At block 1330, the process 1300 includes determining a group of securityevents. The group of security events is determined using the securityinformation. Each security event of the group of security eventsincludes a field value specified by a criteria. To illustrate, the eventaggregator engine 235 of FIG. 2 may determine a group of security eventsidentified from the time stamped search events for which the filteringengine 230, at block 1235, extracted values for a field. Each of thegroup of security events corresponds to a time stamped events. The eventaggregator engine 235 may identify the time stamped events within thetime period that have an extracted field value that satisfies thecriteria. The criteria may include a value for one or more fields thatrelates to events associated with computer or network security. Forexample, the criteria may include a particular length of a uniformresource locator (URL) string, a source address, or both. The criteriamay be established to identify events from a particular source of thesource address that may pose a security threat by sending requests usingan URL string of a particular length. Such events may be investigatedfurther by being gathered for further analysis. The event aggregatorengine 235 may determine the group of security events based on the timestamped events having a field specifying the criteria.

The process 1300 continues to block 1335 where a graphical interface ispresented including a summary of the group of security events, othersummaries of security events, and a remove element. The remove elementis associated with the summary. For example, the display interfaceengine 225 of FIG. 2 may generate a graphical interface 192 of FIG. 1 topresent a summary of the group of security events determined at block1330. The graphical interface 192 may include other summaries ofsecurity events. The graphical interface 192 may include a removeelement (e.g. a “whitelist” selection control) that is an interactiveelement associated with the summary. For example, the summary mayinclude a summary of information based on time stamped eventscorresponding to the group of security events of the summary. The othersummaries of the security events may include similar information as thesummary or alternatively, may include other information specific toevents associated with the other summaries. Examples of informationincluded in the summary and the other summaries is described withrespect to FIGS. 2, 4, 5, and 7-9.

At block 1340, input is received corresponding to an interaction of theremove element. Interaction with the remove element causes the summaryto be removed (or “whitelisted”) from the graphical interface displayingthe other summaries of security events. For example, the displayinterface engine 225 of FIG. 2 may receive input corresponding to aninteraction of the remove element 440 of FIG. 4 associated with thesummary of security events 410. In response to the input, the displayinterface engine 225 may remove the summary 410 from the graphicalinterface 400. The graphical interface may still display the othersummaries 420, 430.

At block 1345, the graphical interface is updated to remove the summaryfrom the graphical interface that displays the other summaries ofsecurity events. For example, the display interface engine 235 of FIG. 2may remove the summary 410 of FIG. 4 from the graphical interface 400that display the other summaries 420, 430.

FIG. 14 illustrates a flowchart of an embodiment of a process 1400performed by a security monitoring system. For example, the process 1400may be performed by the security monitoring system 150 of FIG. 1 and/orthe security monitoring system 200 of FIG. 2.

The process 1400 begins at block 1405, where machine data is receivedfrom a data store. The process continues to block 1410 where a summaryof a group of security events is produced. The security events arederived from machine data and are of a type used in a securityinformation and event management field to analyze security issues.Producing the summary comprises discarding event information using adata reduction model.

At block 1415, the process 1400 includes presenting a graphicalinterface including the summary of the group of security events, othersummaries of security events, and a remove element. The remove isassociated with the summary. Continuing to block 1420, the process 1400includes receiving input corresponding to an interaction of the removeelement. Interacting with the remove element causes the summary to beremoved from the graphical interface that displays the other summariesof security events. At block 1425, the graphical interface is updated toremove the summary from the graphical interface that displays the othersummaries of security events.

Embodiments of the subject matter and the functional operationsdescribed in this specification can be implemented in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Embodiments ofthe subject matter described in this specification can be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a computer readable medium forexecution by, or to control the operation of, data processing apparatus.

The computer readable medium can be a machine readable storage device, amachine readable storage substrate, a memory device, a composition ofmatter effecting a machine readable propagated signal, or a combinationof one or more of them. The term “data processing apparatus” encompassesall apparatus, devices, and machines for processing data, including byway of example a programmable processor, a computer, or multipleprocessors or computers. The apparatus can include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, or acombination of one or more of them, A propagated signal is anartificially generated signal, e.g., a machine generated electrical,optical, or electromagnetic signal, that is generated to encodeinformation for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, softwareapplication, script, or code), can be written in any form of programminglanguage, including compiled or interpreted languages, and it can bedeployed in any form, including as a stand alone program or as a module,component, subroutine, or other unit suitable for use in a computingenvironment. A computer program does not necessarily correspond to afile in a file system. A program can be stored in a portion of a filethat holds other programs or data (e.g., on or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto optical disks, or optical disks. However, a computerneed not have such devices. Moreover, a computer can be embedded inanother device, e.g., a mobile telephone, a personal digital assistant(PDA), a mobile audio player, a Global Positioning System (GPS)receiver, to name just a few. Computer readable media suitable forstoring computer program instructions and data include all forms ofnonvolatile memory, media, and memory devices, including by way ofexample semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD ROM disks. Theprocessor and the memory can be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, architecture provider orreviewer, embodiments of the subject matter described in thisspecification can be implemented on a computer having a display device,e.g., a CRT (cathode ray tube) to LCD (liquid crystal display) monitor,for displaying information to the user and a keyboard and a pointingdevice, e.g., a mouse or a trackball, by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user, architecture provider or reviewer as well; forexample, feedback provided to the user can be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user, architecture provider or reviewer can bereceived in any from, including acoustic, speech, or tactile input.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front end component, e.g., aclient computer having a graphical interface or a Web browser throughwhich a user can interact with an implementation of the subject matterdescribed in this specification, or any combination of one or more suchback end, middleware, or front end components. The components of thesystem can be interconnected by any form or medium of digital datacommunication, e.g., a communication network. Examples of communicationnetworks include a local area network (“LAN”) and a wide area network(“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client server relationship to each other.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the invention or of what may beclaimed, but rather as descriptions of features specific to particularembodiments of the invention. Certain features that are described inthis specification in the context or separate embodiments can also beimplemented in combination in a single embodiment. Conversely, variousfeatures that are described in the context of a single embodiment canalso be implemented in multiple embodiments separately or in anysuitable subcombination. Moreover, although features may be describedabove as acting in certain combinations and even initially claimed assuch, one or more features from a claimed combination can in some casesbe excised from the combination, and the claimed combination may bedirected to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the invention have been described.

Other embodiments are within the scope of the following claims. Forexample, the actions recited in the claims can be performed in adifferent order and still achieve desirable results.

What is claimed is:
 1. A method comprising: creating, by a computersystem, an event group, the event group including a plurality of events,each event in the event group having a respective portion of machinedata, wherein each event in the event group is included in the eventgroup based on an event matching criterion relating to one or more fieldvalues of a respective one or more fields present in a respectiveportion of machine data; creating, by the computer system, an eventgroup summary that summarizes one or more fields present in the portionof machine data included in the plurality of events included in theevent group; causing, by the computer system, display of a graphicaluser interface that includes a plurality of event group summariesincluding the event group summary; receiving, by the computer system,one or more new events, each having a respective portion of machinedata; and in response to receiving the one or more new events,identifying, by the computer system, the one or more new events asbelonging to the event group, and modifying, by the computer system, theevent group summary based upon one or more fields present in the machinedata contained in the one or more new events.
 2. The method of claim 1,further comprising: receiving first input indicating selection of theevent group summary; receiving second input indicating a time frame; andsuppressing, by the computer system, display of the event group summaryby removing the event group summary from the graphical user interface,wherein the event group summary is suppressed during the time frameindicated by the second input.
 3. The method of claim 1, wherein atleast one event group summary of the plurality of event group summariesincludes domain activity information.
 4. The method of claim 1, furthercomprising: changing, by the computer system, a visual appearance of aparticular event group summary among the plurality of event groupsummaries to indicate that the particular event group summary is apotential security threat.
 5. The method of claim 1, further comprising:causing, by the computer system, display of a second graphical userinterface displaying a second plurality of event group summariesincluding the selected event group summary, wherein each event groupsummary in the second plurality of event group summaries was removedfrom the plurality of event group summaries indicating that each eventgroup summary in the second plurality of event group summaries is not asecurity threat.
 6. The method of claim 1, wherein the machine datacomprises log data; the method further comprising: organizing themachine data into the plurality of time-stamped events, wherein an eventcomprises at least a portion of log data within the machine data.
 7. Themethod of claim 1, wherein each event of the plurality of events isassociated with a time stamp, and wherein the event group summaryencompasses events having time stamps within a specified time period. 8.The method of claim 1, wherein the event group summary includes anumerical count of events in the event group.
 9. The method of claim 1,wherein the criterion includes at least one of: an HTTP agent string, anetwork traffic size, a length of a uniform resource locator string, abyte count per request, a domain name, or a source address.
 10. Themethod of claim 1, wherein the criterion includes a particular thresholdstring length for the one or more extracted field values.
 11. The methodof claim 1, wherein the criterion includes a particular threshold stringlength for a network resource locator.
 12. The method of claim 1,wherein the criterion includes a source address associated with asecurity threat.
 13. The method of claim 1, further comprising:generating, by the computer system, a display that includes an addelement and one or more event group summaries that have been removedfrom the graphical interface, wherein the one or more event groupsummaries include the event group summary, and wherein a userinteraction with the add element causes the event group summary to beadded back to the graphical interface; and in response to a userinteraction with the add element, updating, by the computer system, thegraphical interface to add the event group summary back to the graphicalinterface.
 14. The method of claim 1, wherein each event in theplurality of events includes information relating to security of aninformation technology environment.
 15. A non-transitorymachine-readable storage medium storing instructions, execution of whichin a computer system causes performance by the computer system ofoperations comprising: creating an event group, the event groupincluding a plurality of events, each event in the event group having arespective portion of machine data, wherein each event in the eventgroup is included in the event group based on an event matchingcriterion relating to one or more field values of a respective one ormore fields present in a respective portion of raw machine data;creating an event group summary that summarizes one or more fieldspresent in the portion of machine data included in the plurality ofevents included in the event group; causing display of a graphical userinterface that includes a plurality of event group summaries includingthe event group summary; receiving one or more new events, each having arespective portion of machine data; and in response to receiving the oneor more new events, identifying the one or more new events as belongingto the event group, and modifying the event group summary based upon oneor more fields present in the machine data contained in the one or morenew events.
 16. The non-transitory machine-readable storage medium ofclaim 15, wherein said operations further comprise: segmenting storedmachine data into the plurality of events, wherein each event in theplurality of events includes information relating to security of aninformation technology environment.
 17. The non-transitorymachine-readable storage medium of claim 15, wherein said operationsfurther comprise: extracting values for fields in events in the eventgroup, by applying a late binding schema to at least a portion of theplurality of events.
 18. A computer system comprising: a networkinterface via which to communicate with a remote computer system over anetwork; a memory; and a processor coupled to the memory and the networkinterface and configured to cause the system to perform operationsincluding: creating an event group, the event group including aplurality of events, each event in the event group having a respectiveportion of machine data, wherein each event in the event group isincluded in the event group based on an event matching criterionrelating to one or more field values of a respective one or more fieldspresent in a respective portion of raw machine data; creating an eventgroup summary that summarizes one or more fields present in the portionof machine data included in the plurality of events included in theevent group; causing display of a graphical user interface that includesa plurality of event group summaries including the event group summary;receiving one or more new events, each having a respective portion ofmachine data; and in response to receiving the one or more new events,identifying the one or more new events as belonging to the event group,and modifying the event group summary based upon one or more fieldspresent in the machine data contained in the one or more new events. 19.The computer system of claim 18, wherein said operations furthercomprise: causing display of a second graphical user interfacedisplaying a second plurality of event group summaries including theselected event group summary, wherein each event group summary in thesecond plurality of event group summaries was removed from the pluralityof event group summaries indicating that each event group summary in thesecond plurality of event group summaries is not a security threat. 20.The computer system of claim 18, wherein at least one event groupsummary of the plurality of event group summaries includes domainactivity information.